Skip to content

build: update all non-major dependencies (main)#32920

Open
angular-robot wants to merge 1 commit intoangular:mainfrom
angular-robot:ng-renovate/main-all-non-major-dependencies
Open

build: update all non-major dependencies (main)#32920
angular-robot wants to merge 1 commit intoangular:mainfrom
angular-robot:ng-renovate/main-all-non-major-dependencies

Conversation

@angular-robot
Copy link
Copy Markdown
Contributor

@angular-robot angular-robot commented Apr 2, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@eslint/compat (source) 2.0.32.0.4 age adoption passing confidence
@modelcontextprotocol/sdk (source) 1.28.01.29.0 age adoption passing confidence
@rollup/wasm-node (source) 4.60.04.60.1 age adoption passing confidence
@tony.ganchev/eslint-plugin-header ~3.3.1~3.4.0 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 8.57.28.58.0 age adoption passing confidence
@typescript-eslint/parser (source) 8.57.28.58.0 age adoption passing confidence
algoliasearch (source) 5.50.05.50.1 age adoption passing confidence
esbuild 0.27.30.28.0 age adoption passing confidence
esbuild-wasm 0.27.30.28.0 age adoption passing confidence
eslint (source) 10.1.010.2.0 age adoption passing confidence
lmdb 3.5.23.5.3 age adoption passing confidence
rolldown (source) 1.0.0-rc.121.0.0-rc.13 age adoption passing confidence
rollup (source) 4.60.04.60.1 age adoption passing confidence
sass 1.98.01.99.0 age adoption passing confidence
undici (source) 7.24.67.24.7 age adoption passing confidence
verdaccio (source) 6.3.26.4.0 age adoption passing confidence

  • If you want to rebase/retry this PR, check this box

Release Notes

eslint/rewrite (@​eslint/compat)

v2.0.4

Compare Source

Dependencies
  • The following workspace dependencies were updated
modelcontextprotocol/typescript-sdk (@​modelcontextprotocol/sdk)

v1.29.0

Compare Source

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/typescript-sdk@v1.28.0...v1.29.0

rollup/rollup (@​rollup/wasm-node)

v4.60.1

Compare Source

2026-03-30

Bug Fixes
  • Resolve a situation where side effect imports could be dropped due to a caching issue (#​6286)
Pull Requests
tonyganchev/eslint-plugin-header (@​tony.ganchev/eslint-plugin-header)

v3.4.3

Compare Source

  • Support linting YAML using eslint-plugin-yml. Supported for ESLint 9 / 10
    (no oxlint support).

v3.4.2

Compare Source

  • Support linting Svelte sources with top-level HTML comments using
    eslint-plugin-svelte and svelte-eslint-parser. Supported for ESLint 7 / 8
    / 9 / 10. No oxlint support.

v3.4.1

Compare Source

  • Support linting Vue sources with top-level HTML comments using
    eslint-plugin-vue and vue-eslint-parser. Supported for ESLint 7 / 8 / 9
    / 10. No oxlint support.

v3.4.0

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.58.0

Compare Source

🚀 Features
🩹 Fixes
  • eslint-plugin: [prefer-regexp-exec] avoid fixing unknown RegExp flags (#​12161)
  • eslint-plugin: [no-extraneous-class] handle index signatures (#​12142)
  • eslint-plugin: crash in no-unnecessary-type-arguments (#​12163)
❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.58.0

Compare Source

🚀 Features
❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

algolia/algoliasearch-client-javascript (algoliasearch)

v5.50.1

Compare Source

evanw/esbuild (esbuild)

v0.28.0

Compare Source

  • Add support for with { type: 'text' } imports (#​4435)

    The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing text loader. Here's an example:

    import string from './example.txt' with { type: 'text' }
    console.log(string)
  • Add integrity checks to fallback download path (#​4343)

    Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the npm command, and then with a HTTP request to registry.npmjs.org as a last resort).

    This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level esbuild package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.

  • Update the Go compiler from 1.25.7 to 1.26.1

    This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:

    • It now uses the new garbage collector that comes with Go 1.26.
    • The Go compiler is now more aggressive with allocating memory on the stack.
    • The executable format that the Go linker uses has undergone several changes.
    • The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.

    You can read the Go 1.26 release notes for more information.

v0.27.7

Compare Source

  • Fix lowering of define semantics for TypeScript parameter properties (#​4421)

    The previous release incorrectly generated class fields for TypeScript parameter properties even when the configured target environment does not support class fields. With this release, the generated class fields will now be correctly lowered in this case:

    // Original code
    class Foo {
      constructor(public x = 1) {}
      y = 2
    }
    
    // Old output (with --loader=ts --target=es2021)
    class Foo {
      constructor(x = 1) {
        this.x = x;
        __publicField(this, "y", 2);
      }
      x;
    }
    
    // New output (with --loader=ts --target=es2021)
    class Foo {
      constructor(x = 1) {
        __publicField(this, "x", x);
        __publicField(this, "y", 2);
      }
    }

v0.27.5

Compare Source

  • Fix for an async generator edge case (#​4401, #​4417)

    Support for transforming async generators into the equivalent state machine was added in version 0.19.0. However, the generated state machine didn't work correctly when polling async generators concurrently, such as in the following code:

    async function* inner() { yield 1; yield 2 }
    async function* outer() { yield* inner() }
    let gen = outer()
    for await (let x of [gen.next(), gen.next()]) console.log(x)

    Previously esbuild's output of the above code behaved incorrectly when async generators were transformed (such as with --supported:async-generator=false). The transformation should be fixed starting with this release.

    This fix was contributed by @​2767mr.

  • Fix a regression when metafile is enabled (#​4420, #​4418)

    This release fixes a regression introduced by the previous release. When metafile: true was enabled in esbuild's JavaScript API, builds with build errors were incorrectly throwing an error about an empty JSON string instead of an object containing the build errors.

  • Use define semantics for TypeScript parameter properties (#​4421)

    Parameter properties are a TypeScript-specific code generation feature that converts constructor parameters into class fields when they are prefixed by certain keywords. When "useDefineForClassFields": true is present in tsconfig.json, the TypeScript compiler automatically generates class field declarations for parameter properties. Previously esbuild didn't do this, but esbuild will now do this starting with this release:

    // Original code
    class Foo {
      constructor(public x: number) {}
    }
    
    // Old output (with --loader=ts)
    class Foo {
      constructor(x) {
        this.x = x;
      }
    }
    
    // New output (with --loader=ts)
    class Foo {
      constructor(x) {
        this.x = x;
      }
      x;
    }
  • Allow es2025 as a target in tsconfig.json (#​4432)

    TypeScript recently added es2025 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
      "compilerOptions": {
        "target": "ES2025"
      }
    }

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

v0.27.4

Compare Source

  • Fix a regression with CSS media queries (#​4395, #​4405, #​4406)

    Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the <media-type> and <media-condition-without-or> grammar. Specifically, esbuild was failing to wrap an or clause with parentheses when inside <media-condition-without-or>. This release fixes the regression.

    Here is an example:

    /* Original code */
    @&#8203;media only screen and ((min-width: 10px) or (min-height: 10px)) {
      a { color: red }
    }
    
    /* Old output (incorrect) */
    @&#8203;media only screen and (min-width: 10px) or (min-height: 10px) {
      a {
        color: red;
      }
    }
    
    /* New output (correct) */
    @&#8203;media only screen and ((min-width: 10px) or (min-height: 10px)) {
      a {
        color: red;
      }
    }
  • Fix an edge case with the inject feature (#​4407)

    This release fixes an edge case where esbuild's inject feature could not be used with arbitrary module namespace names exported using an export {} from statement with bundling disabled and a target environment where arbitrary module namespace names is unsupported.

    With the fix, the following inject file:

    import jquery from 'jquery';
    export { jquery as 'window.jQuery' };

    Can now always be rewritten as this without esbuild sometimes incorrectly generating an error:

    export { default as 'window.jQuery' } from 'jquery';
  • Attempt to improve API handling of huge metafiles (#​4329, #​4415)

    This release contains a few changes that attempt to improve the behavior of esbuild's JavaScript API with huge metafiles (esbuild's name for the build metadata, formatted as a JSON object). The JavaScript API is designed to return the metafile JSON as a JavaScript object in memory, which makes it easy to access from within a JavaScript-based plugin. Multiple people have encountered issues where this API breaks down with a pathologically-large metafile.

    The primary issue is that V8 has an implementation-specific maximum string length, so using the JSON.parse API with large enough strings is impossible. This release will now attempt to use a fallback JavaScript-based JSON parser that operates directly on the UTF8-encoded JSON bytes instead of using JSON.parse when the JSON metafile is too big to fit in a JavaScript string. The new fallback path has not yet been heavily-tested. The metafile will also now be generated with whitespace removed if the bundle is significantly large, which will reduce the size of the metafile JSON slightly.

    However, hitting this case is potentially a sign that something else is wrong. Ideally you wouldn't be building something so enormous that the build metadata can't even fit inside a JavaScript string. You may want to consider optimizing your project, or breaking up your project into multiple parts that are built independently. Another option could potentially be to use esbuild's command-line API instead of its JavaScript API, which is more efficient (although of course then you can't use JavaScript plugins, so it may not be an option).

eslint/eslint (eslint)

v10.2.0

Compare Source

Features

Bug Fixes

Documentation

  • a2af743 docs: add language to configuration objects (#​20712) (Francesco Trotta)
  • 845f23f docs: Update README (GitHub Actions Bot)
  • 5fbcf59 docs: remove sourceType from ts playground link (#​20477) (Tanuj Kanti)
  • 8702a47 docs: Update README (GitHub Actions Bot)
  • ddeaded docs: Update README (GitHub Actions Bot)
  • 2b44966 docs: add Major Releases section to Manage Releases (#​20269) (Milos Djermanovic)
  • eab65c7 docs: update eslint versions in examples (#​20664) (루밀LuMir)
  • 3e4a299 docs: update ESM Dependencies policies with note for own-usage packages (#​20660) (Milos Djermanovic)

Chores

  • 8120e30 refactor: extract no unmodified loop condition (#​20679) (kuldeep kumar)
  • 46e8469 chore: update dependency markdownlint-cli2 to ^0.22.0 (#​20697) (renovate[bot])
  • 01ed3aa test: add unit tests for unicode utilities (#​20622) (Manish chaudhary)
  • 811f493 ci: remove --legacy-peer-deps from types integration tests (#​20667) (Milos Djermanovic)
  • 6b86fcf chore: update dependency npm-run-all2 to v8 (#​20663) (renovate[bot])
  • 632c4f8 chore: add prettier update commit to .git-blame-ignore-revs (#​20662) (루밀LuMir)
  • b0b0f21 chore: update dependency eslint-plugin-regexp to ^3.1.0 (#​20659) (Milos Djermanovic)
  • 228a2dd chore: update dependency eslint-plugin-eslint-plugin to ^7.3.2 (#​20661) (Milos Djermanovic)
  • 3ab4d7e test: Add tests for eslintrc-style keys (#​20645) (kuldeep kumar)
kriszyp/lmdb-js (lmdb)

v3.5.3

Compare Source

rolldown/rolldown (rolldown)

v1.0.0-rc.13

Compare Source

🚀 Features
🐛 Bug Fixes
🚜 Refactor
📚 Documentation
🧪 Testing
⚙️ Miscellaneous Tasks
❤️ New Contributors
sass/dart-sass (sass)

v1.99.0

Compare Source

  • Add support for parent selectors (&) at the root of the document. These are
    emitted as-is in the CSS output, where they're interpreted as the scoping
    root
    .

  • User-defined functions named calc or clamp are no longer forbidden. If
    such a function exists without a namespace in the current module, it will be
    used instead of the built-in calc() or clamp() function.

  • User-defined functions whose names begin with - and end with -expression,
    -url, -and, -or, or -not are no longer forbidden. These were
    originally intended to match vendor prefixes, but in practice no vendor
    prefixes for these functions ever existed in real browsers.

  • User-defined functions named EXPRESSION, URL, and ELEMENT, those that
    begin with - and end with -ELEMENT, as well as the same names with some
    lowercase letters are now deprecated, These are names conflict with plain CSS
    functions that have special syntax.

    See the Sass website for details.

  • In a future release, calls to functions whose names begin with - and end
    with -expression and -url will no longer have special parsing. For now,
    these calls are deprecated if their behavior will change in the future.

    See the Sass website for details.

  • Calls to functions whose names begin with - and end with -progid:... are
    deprecated.

    See the Sass website for details.

nodejs/undici (undici)

v7.24.7

Compare Source

What's Changed
New Contributors

Full Changelog: nodejs/undici@v7.24.6...v7.24.7

verdaccio/verdaccio (verdaccio)

v6.4.0

Compare Source

Features

Package Filter Plugins (#​5786, #​5548) by @​vsugrob, @​pyhp2017 @​juanpicado

The @verdaccio/package-filter package is bundled by default but must be enabled by the user.

@verdaccio/package-filter is a built-in plugin that intercepts package metadata from uplinks and removes versions matching configurable rules. With no rules configured, it acts as a no-op passthrough.

Block a compromised package version
filters:
  '@&#8203;verdaccio/package-filter':
    block:
      - package: 'event-stream'
        versions: '3.3.6'
Block an entire malicious scope
filters:
  '@&#8203;verdaccio/package-filter':
    block:
      - scope: '@&#8203;malicious'
Quarantine recently published versions

Hide versions published less than 7 days ago, giving time for review before adoption:

filters:
  '@&#8203;verdaccio/package-filter':
    minAgeDays: 7
Freeze registry to a point in time

Only serve versions published before a specific date:

filters:
  '@&#8203;verdaccio/package-filter':
    dateThreshold: '2025-01-01'
Whitelist trusted packages within blocked rules
filters:
  '@&#8203;verdaccio/package-filter':
    minAgeDays: 30
    allow:
      - scope: '@&#8203;my-company'
      - package: 'trusted-pkg'
Replace instead of remove

Substitute a blocked version with the nearest older safe version, useful when removing it would break transitive dependencies:

filters:
  '@&#8203;verdaccio/package-filter':
    block:
      - package: 'compromised-lib'
        versions: '>=3.0.0'
        strategy: replace
Full example
filters:
  '@&#8203;verdaccio/package-filter':
    minAgeDays: 7
    block:
      - scope: '@&#8203;malicious'
      - package: 'typosquat-pkg'
      - package: 'compromised-lib'
        versions: '>=3.0.0'
        strategy: replace
    allow:
      - scope: '@&#8203;my-org'
      - package: 'compromised-lib'
        versions: '3.0.1'

Bug Fixes

Full Changelog: verdaccio/verdaccio@v6.3.2...v6.4.0

@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] labels Apr 2, 2026
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates several dependencies, including @modelcontextprotocol/sdk, rollup, and various @typescript-eslint packages. The review highlights that despite the version bumps in package.json, the pnpm-lock.yaml file still contains references to older versions of @typescript-eslint and rollup for certain packages within the monorepo. It is recommended to fully synchronize these versions across the entire dependency graph to ensure consistency and avoid potential build issues.

@angular-robot angular-robot force-pushed the ng-renovate/main-all-non-major-dependencies branch 8 times, most recently from 6d7cf1e to 401708b Compare April 4, 2026 21:09
@angular-robot angular-robot force-pushed the ng-renovate/main-all-non-major-dependencies branch from 401708b to 0022759 Compare April 6, 2026 23:14
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/main-all-non-major-dependencies branch from 0022759 to 3a3490b Compare April 7, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants